Method for reproducing configuration of a computer system in a remote site

ABSTRACT

A computer system formerly handles a service that is quickly reproduced with another computer system to resume the service immediately. The association relations between services run by a primary site ( 1 ) and primary site servers ( 13 ), between the primary site servers ( 13 ) and a primary site storage system ( 15 ), and between the storage system ( 15 ) of the primary site ( 1 ) and a storage system ( 25 ) of a secondary site ( 2 ) are collected. The collected association relations are copied as configuration information from the storage system ( 15 ) of the primary site ( 1 ) to the secondary site ( 2 ). On the secondary site ( 2 ), based on the copied configuration information, services of the primary site ( 1 ) are assigned to servers ( 23 ) of the secondary site ( 2 ), and the secondary site servers ( 23 ) are associated with the storage system ( 25 ) of the secondary site ( 2 ) to reproduce the primary site ( 1 ) thereon.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation Application of U.S. application Ser.No. 11/202,196 filed on Aug. 12, 2005 now U.S. Pat. No. 7,610,362. Thepresent application claims priority from U.S. application Ser. No.11/202,196 filed on Aug. 12, 2005, which claims priority from Japaneseapplication 2005-111809 filed on Apr. 8, 2005, the content of which ishereby incorporated by reference into this application.

BACKGROUND OF THE INVENTION

This invention relates to a technique of reproducing a configuration fora system that is to take over a server or a service in the event offailover, server integration, or the like.

It is very important for a business to continue providing servicesdespite failures and disasters, and disaster recovery systems are knownin the field of Information Technology (IT) systems. In a disasterrecovery system, two sites, primary and secondary, which can exchangedata with each other are prepared, and data of a service of the primarysite is constantly backed up to the secondary site so that the serviceis kept provided after a disaster or the like on the secondary site.

The secondary site has to have the same server and network configurationas the primary site in order to resume the service after a failure or adisaster damages the primary site with the use of the data backed up tothe secondary site (the secondary site is reconfigured to have the sameconfiguration as the primary site). In a known method, the administratorof the secondary site sets, in advance, a configuration settingprocedure in the form of script or the like, and the script is executedto reconfigure the secondary site as a recovery operation to startproviding the service on the secondary site (see U.S. Pat. No.6,636,988, for example).

The script contains server processor definitions, OS settingsdefinitions, storage system definitions, network definitions, and thelike that are manually set by the administrator in advance.

SUMMARY OF THE INVENTION

However, even with a script as the one described above, it could takehalf a day to several days since reconfiguration of the secondary siteis started until the service is ready to be resumed. The method using ascript is not capable of reconfiguring the secondary site quickly andeasily for the following reasons:

One is that every change in configuration of the primary site has to bereflected on the script of the secondary site. Updating the scriptmanually from day to day is very labor-consuming and raises themanagement cost since, on the primary site, an increase in capacity tostore data makes changes to a storage system or volume where data isstored, a change in server processing load changes a server or aprocessor, and a change in server or storage system changes theconfiguration of an IP (Internet Protocol) network and a SAN (StorageArea Network).

Another reason is that it is common for the secondary site to keep itsstorage system and server computer in operation constantly and havethese computer resources perform a service different from the oneprovided by the primary site in order to make full use of the primarysite and the secondary site. In the case where the service provided bythe secondary site cannot be halted for the recovery of the service ofthe primary site, reconfiguration of the secondary site will becomplicated from shortage of computer resources and overlapping ofnetwork definitions (e.g., VLAN IDs) and accordingly take longer time.

In recent years, a technique using a blade server, which can switchcomputers on a substrate basis, has been introduced to enable an ITsystem to change its configuration more flexibly. With this technique, amultitude of servers can now be integrated into a blade server (serverconsolidation or server integration).

Reconfiguration of an old system to a new system for server integrationrelies mostly on manual labor as in the recovery operation describedabove. Thus the transition from an old system to a new system takes aconsiderable amount of time.

This invention has been made in view of the above problems, and it istherefore an object of this invention to provide a technique of quicklyreproducing a computer system that has formerly handled a service withanother computer system to resume the service immediately.

This invention relates to a method of causing a second computer system,which has server devices and a storage system, to execute a service orservices that have been executed by a first computer system, which hasserver devices and a storage system, the method including, to reproducethe first computer system in the second computer system: collectingservice-server device association relations between the services and theserver devices that are run in the first computer system; collectingserver device-storage system association relations in the first computersystem; collecting an association relation between the storage system ofthe first computer system and the storage system of the second computersystem; storing as configuration information, in the storage system ofthe first computer system, the service-server device associationrelations in the first computer system, the server device-storage systemassociation relations in the first computer system, and the associationrelation between the storage system of the first storage system and thesecond computer system; copying data of the services of the firstcomputer system and the stored configuration information to the secondcomputer system; assigning services of the first computer system toserver devices of the second computer system based on the copiedconfiguration information of the first computer system; and associatingthe server devices of the second computer system, to which the servicesof the first computer system are assigned, with the storage system ofthe second computer system based on the configuration information.

According to this invention, with configuration information of the firstcomputer system copied to the second computer system, the first computersystem can automatically be reproduced in the second computer systemfrom the copy of the configuration information no matter how manychanges are made to the configuration of a server device, a storagesystem, and the like in the first computer system.

Since the first computer system can be reproduced automatically unlikethe above-described examples of prior art where human intervention isnecessary, the second computer system can be reconfigured very quickly.In application to recovery from disaster, in particular, the secondcomputer system can take over the first computer system within a veryshort period of time, which shortens the service interruption periodsignificantly and minimizes the damage to the company or organization.

In application to server integration, the administrator can useconfiguration information of the first computer system to automaticallyintegrate servers into the second computer system. Thus, the enormousamount of labor and time required in conventional server integration iscut down greatly and a new computer system can start operating insignificantly less time after introduction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a disaster recovery system accordingto a first embodiment of this invention.

FIG. 2 is a block diagram showing a server configuration.

FIG. 3 is a block diagram showing the relations between services and acomputer system on a primary site.

FIG. 4 is a block diagram showing the relation between the computersystem on the primary site and a storage system on a secondary site.

FIG. 5 is a block diagram showing a configuration information managementfacility set up on the primary site and the secondary site each.

FIG. 6 is a block diagram showing the relations between services of theprimary site and services of the secondary site.

FIG. 7 is an explanatory diagram showing an example of a servicemanagement table in the configuration information management facility.

FIG. 8 is an explanatory diagram showing an example of a servermanagement table in the configuration information management facility.

FIG. 9 is an explanatory diagram showing an example of a network switchmanagement table in the configuration information management facility.

FIG. 10 is an explanatory diagram showing an example of a storage switchmanagement table in the configuration information management facility.

FIG. 11 is an explanatory diagram showing an example of a storagemanagement table in the configuration information management facility.

FIG. 12 is a flow chart showing an example of processing performed by aconfiguration information fetching/storing function of the configurationinformation management facility.

FIG. 13 is a flow chart showing an example of processing performed by are-creation function of the configuration information managementfacility.

FIG. 14 is an explanatory diagram showing an example of a table obtainedby compiling service management tables of the primary site and thesecondary site.

FIG. 15 is a flow chart showing an example of processing performed by aserver selecting function of the configuration information managementfacility.

FIG. 16 is an explanatory diagram showing how a server is selected.

FIG. 17 is a flow chart showing an example of processing performed by anetwork switch setting function of the configuration informationmanagement facility.

FIG. 18 is a flow chart showing an example of processing performed by astorage switch setting function of the configuration informationmanagement facility.

FIG. 19 is a flow chart showing an example of processing performed by astorage setting function of the configuration information managementfacility.

FIG. 20 is a block diagram showing the relations between services andcomputer systems on which server integration is performed according to asecond embodiment of this invention.

FIG. 21 is a flow chart showing an example of processing performed by aservice selecting function of a configuration information managementfacility according to a third embodiment of this invention.

FIG. 22 is a flow chart showing an example of processing performed by aserver partitioning function of a service selecting function accordingto the third embodiment.

FIG. 23 is a server block diagram showing an example of logicalpartitioning according to the third embodiment.

FIG. 24 is a server block diagram showing an example of a virtualcomputer according to the third embodiment.

FIG. 25 is an explanatory diagram showing an example of a servermanagement table in the configuration information management facilityaccording to the third embodiment.

FIG. 26 is an explanatory diagram showing an example of a storagemanagement table in a configuration information management facilityaccording to a fourth embodiment of this invention.

FIG. 27 is a flow chart showing an example of processing performed by astorage setting function of the configuration information managementfacility according to the fourth embodiment.

FIG. 28 is a block diagram showing an example of a security function ofa storage system according to the fourth embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Embodiments of this invention will be described below with reference tothe accompanying drawings.

FIG. 1 shows, as a first embodiment of this invention, an example ofapplying this invention to disaster recovery in which data of a computersystem on a primary site 1 is copied to a computer system on a secondarysite 2.

The computer system on the primary site 1 (first computer system) hasplural servers (server devices) 13 to provide a given service with theuse of data stored in a storage system 15. A copy of the data stored inthe storage system 15 of the primary site 1 is transferred to and storedin a storage system 25 of the secondary site 2 through a remote copyfunction via an inter-storage network 3. The remote copy function usedto transfer data from the storage system 15 performs synchronous remotecopy or asynchronous remote copy. The storage system 15 or 25 may not bea single storage system but may be a group of storage systems.

The plural servers 13 of the primary site 1 are connected to one anothervia an IP network 16, which is built around a network switch 12. Theservers 13 are connected to the storage system 15 via a Storage AreaNetwork (SAN) 17, which is built around a Fibre Channel switch 14.

Connected to the IP network 16 is a management server 11, which managesthe configuration of the primary site 1. The management server 11 has aconfiguration information management facility 110 running to obtain andmanage information on the configuration of the primary site 1, includingthe hardware configuration, the software configuration and the networkconfiguration. When there is a change in configuration of the primarysite 1, or at other given timing, the configuration informationmanagement facility 110 obtains the above configuration information ofthe primary site 1, and stores the obtained configuration information ina configuration information storing area 152, which is set in advance inthe storage system 15.

The IP network 16 is also connected to the SAN 17 and to the storagesystem 15. Over the IP network 16, the management server 11 collects theconfiguration information of the primary site 1 and stores the collectedinformation in the configuration information storing area 152 of thestorage system 15.

The servers 13, which provide given services, access a data storing area151, which is set in advance in the storage system 15, via the SAN 17 torefer to or update service data stored in the data storing area 151.

The storage system 15 uses the remote copy function to copy data in thedata storing area 151 and in the configuration information storing area152 to the storage system 25 of the secondary site 2 which is set inadvance. The storage system 25 stores the copy of data in the datastoring area 151 of the primary site 1 in a data storing area 251, whichis set in advance, and stores the copy of data in the configurationinformation storing area 152 of the primary site 1 in a configurationinformation storing area 252, which is set in advance. Applications ofservices executed by the servers 13 and boot images of OSs and otherprograms of the servers 13 are stored in a given image storing area 153.In this way, software necessary for a service provided by the primarysite 1 can automatically be transferred to an image storing area 253 ofthe secondary site 2 through remote copy.

The computer system on the secondary site 2 (second computer system),which keeps a copy of data of services provided by the primary site 1and a copy of configuration information of the primary site 1, issimilar to the computer system on the primary site 1 in that pluralservers (server devices) 23 are connected to a management server 21 viaan IP network 26, which is built around a network switch 22, and thatthe servers 23 are connected to the storage system 25 via an SAN 27,which is built around a Fibre Channel switch 24. The IP network 26 isalso connected to the Fibre Channel switch 24 and to the storage system25, thereby enabling the management server 21 to access the SAN 27 andthe storage system 25.

The management server 21 has a configuration information managementfacility 210 running to obtain and manage information on theconfiguration (hardware configuration, software configuration andnetwork configuration) of the secondary site 2. The configurationinformation management facility 210 has a re-creation facility (programmodule) 112, which, upon instruction from an administrator or the like,reads configuration information of the primary site 1 out of theconfiguration information storing area 252 of the storage system 25 tore-create the configuration and services of the primary site 1 on thesecondary site 2. The administrator accesses the management server 21via a terminal connected to the IP network 26, or the like.

On the secondary site 2, the servers 23 and the storage system 25 canprovide services different from those provided by the primary site 1.

The network switch 12 or 22 may not be a single network switch but maybe a group of network switches. The Fibre Channel switch 14 or 24 maynot be a single Fibre Channel switch but may be a group of Fibre Channelswitches.

FIG. 2 is a block diagram showing the configuration of the servers 13 ofthe primary site 1. The servers 13 are each equipped with a memory 131,which is accessed by a processor 132, a Network Interface Card (NIC)136, which converts signals when the processor 132 access the IP network16, and a Fibre Channel Adapter (FCA) 133, which converts signals whenthe processor 132 accesses the SAN 17.

The FCA 133 has a World Wide Name (WWN), which is a globally uniqueidentifier, and communicates with the SAN 17 through a communicationfacility 135. The NIC 136 has Media Access Control (MAC) 137, which is aglobally unique identifier, and communicates with the IP network 16through a communication facility 138.

The servers 23 of the secondary site 2 have a configuration similar tothat of the servers 13, and redundant descriptions will be omitted.

FIG. 3 is a block diagram showing an example of how services areprovided by the primary site 1. With service identifiers defined in aservice management table, which will be described later with referenceto FIG. 7, the primary site 1 is logically partitioned into VLAN groupsof the IP network 16 and zones of the SAN 17, and is set to avoidoverlapping of access between services. In the example of FIG. 3, theprimary site 1 has five servers 13-1 to 13-5, which are partitioned intothree service groups. The service-providing servers of the primary site1 are generically denoted by 13, and individually denoted by 13-1 to13-5.

The network switch 12 (IP network 16) is divided into three VLAN groups(VLANs 10, 20 and 30) whereas the Fibre Channel switch 14 (SAN 17) isdivided into three zones (Zone 10, 20 and 30). The VLAN groups and thezones are identified by identifiers 10, 20 and 30.

The service group that provides Service One is constituted of twoservers, 13-1 and 13-2, allocated to VLAN 10 and Zone 10. The servers13-1 and 13-2 are connected to client computers (not shown) via VLAN 10of the IP network 16, and the client computers receive Service Oneexecuted by the servers 13-1 and 13-2.

The servers 13-1 and 13-2 access the data storing area 151 of thestorage system 15 via Zone 10 of the SAN 17.

Assigned as the data storing area 151 here are logical disks LU0 to LU3,LU00 and LU01, which are set in advance in the storage system 15. Thelogical disks LU0, LU1 and LU3 are allocated to Zone 10 to which theservers 13-1 and 13-2 belong.

The service group that provides Service Two is constituted of the server13-3, which is allocated to VLAN 20 and Zone 20. The server 13-3 isconnected to client computers (not shown) via VLAN 20 of the IP network16, and the client computers receive Service Two executed by the server13-3.

The server 13-3 accesses the data storing area 151 of the storage system15 via Zone 20 of the SAN 17. Assigned as a portion of the data storingarea 151 for Service Two is the logical disk LU00.

The service group that provides Service Three is constituted of twoservers, 13-4 and 13-5, allocated to VLAN 30 and Zone 30. The servers13-4 and 13-5 are connected to not-shown client computers via VLAN 30 ofthe IP network 16, and the client computers receive Service Threeexecuted by the servers 13-4 and 13-5.

The servers 13-4 and 13-5 access the data storing area 151 of thestorage system 15 via Zone 30 of the SAN 17. Assigned as a portion ofthe data storing area 151 for Service Three is the logical disk LU01.

Given logical disks are assigned as the configuration informationstoring area 152 and as the image storing area 153. For instance, thelogical disk LU2, which will be described later with reference to FIG.4, is set as these storing areas.

FIG. 4 is a block diagram illustrating details of the configuration ofthe primary site 1 which is shown in FIG. 3. In the example of FIG. 4,the network switch 12 shown in FIG. 1 is constituted of two networkswitches 12-1 (SW1) and 12-2 (SW2), and the storage system 15 isconstituted of two storage systems 15-1 (ST1) and 15-2 (ST2). Thenetwork switches of the primary site 1 are generically denoted by 12 andindividually denoted by 12-1 and 12-2. Similarly, the storage systems ofthe primary site 1 are generically denoted by 15 and individuallydenoted by 15-1 and 15-2.

The server 13-1 (Server One) has two NICs, NIC1 and NIC2. MAC1 is set asan MAC address to NIC1 whereas MAC2 is set to NIC2. IP1 is set as an IPaddress to NIC1 whereas IP2 is set to NIC2.

The servers 13-2 to 13-5 (Server Two to Server Five) each have one NIC(NIC3 to NIC6). MAC3 to MAC6 are set as MAC addresses to NIC3 to NIC6,respectively. IP3 to IP6 are assigned as IP addresses to NIC3 to NIC6,respectively. NIC1 to NIC3 of the servers 13-1 and 13-2, which provideService One, are connected to Port One to Port Three belonging to VLAN10 of the network switch 12-1.

NIC4 of the server 13-3, which provides Service Two, is connected toPort Four belonging to VLAN 20 of the network switch 12-1. NIC5 and NIC6of the servers 13-4 and 13-5, which provide Service Three, are connectedto Port Five and Port Seven belonging to VLAN 30 of the network switches12-1 and 12-2.

Port Six and Port Twelve are connected to the network switches 12-1 and12-2, enabling the network switches 12-1 and 12-2 to access each other.The management server 11, which manages the configuration of the primarysite 1, is connected to Port Eleven of the network switch 12-2.

The server 13-1 (Server One) has two FCAs, FCA1 and FCA2. WWN1 is set asan address to FCA1 whereas WWN2 is set to FCA2.

The servers 13-2 to 13-5 each have one FCA (FCA3 to FCA6). WWN3 to WWN6are set as addresses to FCA3 to FCA6, respectively.

FCA1 to FCA3 of the servers 13-1 and 13-2, which provide Service One,are connected to Port One to Port Three belonging to Zone 10 of theFibre Channel switch 14.

FCA4 of the server 13-3, which provides Service Two, is connected toPort Four belonging to Zone 20 of the Fibre Channel switch 14. FCA5 andFCA6 of the servers 13-4 and 13-5, which provide Service Three, areconnected to Port Five and Port Six belonging to Zone 30 of the FibreChannel switch 14.

Ports P0 and P1 of the storage system 15-1 are connected to Port Sevenand Port Eight of the Fibre Channel switch 14, respectively. Ports P00and P01 of the storage system 15-2 are connected to Port Eleven and PortTwelve of the Fibre Channel switch 14, respectively.

The logical disks LU0 to LU3 are set as the storage system 15-1 whereasthe logical disks LU00 and LU01 are set as the storage system 15-2. Forinstance, the logical disks LU0, LU1, LU3, LU00 and LU01 are set as thedata storing area 151 shown in FIG. 1, while setting the logical diskLU2 as the configuration information storing area 152. Which of theservers 13-1 to 13-5 accesses through a path set as will be describedlater is set for each of the logical disks LU0 to LU3, LU00 and LU11.

Plural logical disks, LU10 to LU13, LU20 and LU21 in the example of FIG.4, are set as the storage system 25 of the secondary site 2, to keepinformation of the primary site 1 through the remote copy function ofthe storage systems 15-1 and 15-2. An example of remote copy settings ofthe storage systems 15-1 and 15-2 is shown in FIG. 4, in which thestorage system 15-1 copies data in the logical disks LU0 to LU3 to thelogical disks LU10 to LU13 of the storage system 25 on the secondarysite 2 whereas the storage system 15-2 copies data in the logical disksLU00 and LU01 to the logical disks LU20 and LU21 of the storage system25 on the secondary site 2. In this example, the logical disks LU0, LU1,LU3, LU00 and LU01 correspond to the data storing area 251 whereas thelogical disk LU2 corresponds to the configuration information storingarea 252.

FIG. 5 is a block diagram showing details of the configurationinformation management facilities 110 and 210 in the management servers11 and 21. The configuration information management facility 110 of theprimary site 1 and the configuration information management facility 210of the secondary site 2 have the same configuration, but executedifferent functions.

The major function in the configuration information management facility110 of the primary site 1 is the configuration informationfetching/storing function 111 with which configuration information 40 ofthe primary site 1 is obtained and stored in the storage system 15.

The configuration information fetching/storing function 111 obtains, atgiven timing, information on the configuration of the servers 13, theconfigurations of the IP network 16 and the SAN 17, and theconfiguration of the storage system 15, and stores the obtainedconfiguration information in the configuration information storing area152 of the storage system 15.

The configuration information 40 is composed of a site identifier 401,which indicates the identifier of a site, a table pointer 402, which isused in consulting tables, a service management table 41 (FIG. 7), whichshows the association relations between services and the servers 13, aserver management table 42 (FIG. 8), which shows components of theservers 13 and whether the servers 13 are in use or not, a networkswitch management table 43 (FIG. 9), which shows the associationrelations between devices connected to the ports of the network switch12 and VLANs, a storage switch management table 44 (FIG. 10), whichshows the association relations between devices connected to the portsof the Fibre Channel switch 14 and zones, and a storage management table45 (FIG. 11), which shows the association relations between the servers13 and the logical disks of the storage system 15 accessed by theservers 13. The service management table 41 can be set by theadministrator or the like.

The service management table 41 is cross-referential to the servermanagement table 42 through server identifiers (403). The network switchmanagement table 43, the storage switch management table 44 and thestorage management table 45 are cross-referential to the servermanagement table 42 (404).

The configuration information fetching/storing function 111 functions inthe management server 21 of the secondary site 2 as well as in themanagement server 11 of the primary site 1, and obtains theconfiguration information 40 of the primary site 1 and of the secondarysite 2 to store the information in the storage systems 15 and 25,respectively. The configuration information 40 is collected each time achange is made to site configuration, each time a given period of timepasses, upon instruction from the administrator, or the like.

In this embodiment, the re-creation function 112 of the configurationinformation management facility 110 (or 210) functions in the managementserver 21 of the secondary site 2.

The re-creation function 112 functioning in the management server 21 ofthe secondary site 2 reads, upon instruction from the administrator orthe like, data and the configuration information 40 of the primary site1 out of the data storing area 251 and the configuration informationstoring area 252, which are in the storage system 25, to performrestoration processing for reproducing a service of the primary site 1on the secondary site 2.

The re-creation function 112 is composed of a service selecting function113, which is for selecting what service is to be reproduced on thesecondary site 2 based on the configuration information of the secondarysite 2 and the configuration information 40 of the primary site 1 thathas been kept by the secondary site 2, a server selecting function 114,which is for selecting which of the servers 23 is to execute theservice, a network switch setting function 115, which is for setting theconfiguration and the like of VLAN groups of the IP network 26, astorage switch setting function 116, which is for zoning the SAN 27, anda storage setting function 117, which is for setting the associationrelations between the servers 23 and the logical disks of the storagesystem 25 accessed by the servers 23. The re-creation function 112reproduces a service of the primary site 1 in accordance with whatcomputer resources are available on the secondary site 2.

Now, an example of service-server relations on the primary site 1 andthe secondary site 2 according to the first embodiment is shown withreference to FIG. 6.

In FIG. 6, on the primary site 1, the servers 13-1 and 13-2 provideService One, the server 13-3 provides Service Two, and the servers 13-4and 13-5 provide Service Three as mentioned above.

The secondary site 2 has five servers 23-1 to 23-5. The server 23-1provides Service Eleven, the server 23-3 provides Service Twelve, theserver 23-5 provides Service Thirteen, and the servers 23-2 and 23-4 areon stand-by.

When the secondary site 2 takes over Service One to Service Three of theprimary site 1 because of a failure on the primary site 1, there-creation function 112 reproduces all of Service One to Service Threeof the primary site 1 and allows the secondary site 2 to continueService Eleven to Service Thirteen in the case where the secondary site2 has enough computer resources available. On the other hand, in thecase where not all of the services of the primary site 1 and thesecondary site 2 combined cannot be executed by the computer resourcesof the secondary site 2, some of the services of the primary site 1 arereproduced and some of the services of the secondary site 2 are providedin accordance with a preset service priority to keep it within theability of the computer resources available.

Described next are details of the configuration information 40, which iscollected by the configuration information fetching/storing function 111of the configuration information management facility 110 of the primarysite 1 and by the configuration information management facility 210 ofthe secondary site 2.

FIG. 7 is an explanatory diagram showing an example of the servicemanagement table 41 of the primary site 1 when the primary site 1 is asshown in FIG. 4.

The service management table 41 is composed of the identifier 401, whichindicates an identifier uniquely assigned to each site, an identifier411, which indicates an identifier uniquely assigned to each service, arecovery priority 412, which indicates a priority level set for eachservice by the administrator or the like, an identifier 413, whichindicates the identifiers of servers that execute services, and arecovery condition 414, which is set for each service by theadministrator or the like.

The priority 412 shows an order in which Service One to Service Threeare reproduced. A smaller value entered as the priority 412 means ahigher priority level. Stored as the server identifier 413 is theidentifier of every server that is executing a service. As the recoverycondition 414, the administrator or the like sets in advance whether aservice needs to be executed or not when the secondary site 2 attemptsto reproduce services of the primary site 1 but does not have enoughcomputer resources available. A service for which “recovery required” isentered as the recovery condition 414 is a service that should bereproduced or executed immediately on the secondary site, such as anessential service of the company or organization.

On the other hand, a service for which “recovery not required” isentered as the recovery condition 414 is a service that does not need tobe reproduced (or executed) immediately and that can wait for whencomputer resources are available. Examples of such services are amonthly report service, a biannual report service, and other similarservices whose temporary suspension does not cause serious damage to thecompany or organization activities.

The configuration information management facility 210 of the secondarysite 2 too has the service management table 41 as the one shown in FIG.7, and the priority and recovery condition 414 are set in advance foreach service provided by the secondary site 2.

In the case where the secondary site 2 attempts to reproduce services ofthe primary site 1 but does not have enough computer resourcesavailable, the re-creation function 112 of the secondary site 2 securesnecessary computer resources by halting a service for which “recoverynot required” is entered as the recovery condition 414 in the servicemanagement table 41 of the secondary site 2. Thereafter, the re-creationfunction 112 reads the service management table 41 of the primary site 1to execute services for which “recovery required” is entered as therecovery condition 414 in an order determined by the priority 412.

FIG. 8 shows an example of the server management table 42 of the primarysite 1 when the primary site 1 is as shown in FIG. 4.

The server management table 42 is composed of the identifier 401, whichindicates an identifier uniquely assigned to each site, an identifier421, which indicates an identifier uniquely assigned to each service, aprocessor classification 422, which indicates the type or the like of aprocessor that constitutes a server, a memory column 423, whichindicates the capacity of a memory a server has, a device column 424,which indicates an NIC or an FCA a server has, an IP address column 425,which indicates an IP address assigned to an NIC of a server, a storagecolumn 426, which indicates a logical disk of a storage system that isassigned to a server, and a status 427, which indicates the currentstate of a server.

The processor classification 422 contains processor information fromwhich the processing ability of a processor can be estimated, forexample, CPU1, which represents a 32-bit processor, and CPU2, whichrepresents a 64-bit processor, and the internal frequency of theprocessor. Other than those shown in FIG. 8, the count of processors,the capacity of the secondary cache, and the like can be entered as theprocessor classification 422.

The device column 424 holds information of devices related to the IPnetwork and the SAN. The identifier and MAC address of an NIC, as wellas the identifier and WWN of an FCA, are stored for each device in thedevice column 424. The IP address column 425 holds the identifier of anNIC and an IP address assigned to this NIC.

Stored in the storage column 426 are a number assigned to a logical diskin a storage system that is allocated to the server identified by theserver identifier 421, the identifier of an FCA that accesses thislogical disk, and the capacity of the logical disk.

Stored as the status 427 is information indicating whether the server isassigned to a service or not. “In use” means that the server is alreadyassigned to a service whereas “not in use” means that the server is onstand-by.

FIG. 9 shows an example of the network switch management table 43 of theprimary site 1 when the primary site 1 is as shown in FIG. 4.

The network switch management table 43 is composed of the identifier401, which indicates an identifier uniquely assigned to each site, anetwork switch identifier 431, which indicates an identifier uniquelyassigned to each network switch, a port number 432, which indicates aport number of a network switch, an MAC address 433, which indicates anMAC address assigned to a port number, a VLAN number (or identifier)434, which indicates a VLAN number assigned to a port number, and aconnected device 435, which indicates the MAC address of a deviceconnected to a port that is identified by the port number 432. In anetwork switch of this embodiment, an MAC address (PMAC in FIG. 9) isassigned to each port number.

In FIG. 9, Switch One entered as the network switch identifier 431represents the network switch 12-1 of FIG. 4 whereas Switch Tworepresents the network switch 12-2.

FIG. 10 shows an example of the storage switch management table 44 ofthe primary site 1 when the primary site 1 is as shown in FIG. 4.

The storage switch management table 44 is composed of the identifier401, which indicates an identifier uniquely assigned to each site, aFibre Channel switch identifier 441, which indicates an identifieruniquely assigned to each Fibre Channel switch, a port number 442, whichindicates a port number of a Fibre Channel switch, a WWN 443, whichindicates a WWN assigned to a port number, a zone number 444, whichindicates a zone number assigned to a port number, and a connecteddevice 445, which indicates the WWN of a device connected to a port thatis identified by the port number 442.

FIG. 11 shows an example of the storage management table 45 of theprimary site 1 when the primary site 1 is as shown in FIG. 4.

The storage management table 45 is composed of the identifier 401, whichindicates an identifier uniquely assigned to each site, a storage systemidentifier 451, which indicates an identifier uniquely assigned to eachstorage system, a server identifier 452, which indicates an identifier(WWN) of a server accessing a storage system that is identified by theserver identifier 452, a disk number 453, which indicates a logical disknumber assigned to a server identifier that is entered as the serveridentifier 452, and a copy destination 454, which indicates theidentifiers and disk number of a site, a server, and a logical diskwhere a copy of data in a logical disk identified by the disk number 453is stored. For example, an entry of FIG. 11 that holds as the serveridentifier 452 WWN1, which represents Server One (the server 13-1) ofthe primary site 1, shows that the logical disks LU0, LU1 and LU3 ofStorage System One (the storage system 15-1) are allocated to ServerOne, and that data in the logical disks LU0, LU1 and LU3 is copied tothe logical disks LU10 to LU13 of the storage system 25 (systemidentifier: 10) on the secondary site 2 (site identifier: 2).Information stored as the copy destination 454 shows the associationrelation between the storage system 15 of the primary site 1 and logicaldisks in the storage system 25 of the secondary site 2.

In FIG. 11, Storage One entered as the storage system identifier 451represents the storage system 15-1 of FIG. 4 whereas Storage Tworepresents the storage system 15-2.

The storage management table 45 shows which servers 13 and 23 assignedto services are associated with which logical disks of storage systemson the primary site 1 and the primary site 2. The logical disk LU2 ofthe storage system 15-2 which is allocated as the configurationinformation storing area 152 to store the configuration information 40of the primary site 1 is set in advance as well as the logical disk LU12of the storage system 25 to which data in the logical disk LU2 iscopied. On the secondary site 2, the configuration information 40 of thesecondary site 2 is stored in logical disks that are not shown in FIG.4.

Described above are the service management table 41, the servermanagement table 42, the network switch management table 43, the storageswitch management table 44, and the storage management table 45 thatconstitute the configuration information 40 of the primary site 1. Theconfiguration information management facility 210 of the secondary site2 too has similar tables, though not illustrated in drawings.

FIG. 12 is a flow chart showing an example of processing performedthrough the configuration information fetching/storing function 111 ofthe configuration information management facility 110 in the managementserver 11 on the primary site 1, or of the configuration informationmanagement facility 210 in the management server 21 on the secondarysite 2. This processing is executed in regular cycles (e.g., every halfhour). The description given below deals with an example of thisprocessing on the primary site 1.

In a step S1, the management server 11 compares the configurationinformation 40 stored in the storage system 15 against the current siteconfiguration. When the current configuration is inconsistent with thestored configuration information, the processing proceeds to a step S2in order to update the configuration information 40. When there is nochange in configuration, the processing is promptly ended.

In a step S2, information on services that are being executed iscollected from the servers 13 to update the service management table 41.

In a step S3, the processor classification 422, the memory 423, thedevice 424, the IP address 425, the allocated storage system 426, andthe status 427 are obtained for each server identifier of the servers 13to update the server management table 42.

In a step S4, the network switch management table 43 is updated byobtaining the VLAN number 434 assigned to ports and the connected device435 for each network switch identifier.

In a step S5, the storage switch management table 44 is updated byobtaining the zone number 444 assigned to ports and the connected device445 for each storage switch identifier.

In a step S6, the storage management table 45 is updated by obtaining,for each of identifiers of the storage systems 15-1 and 15-2, theidentifier 452 of the servers 13 allocated to the storage systems 15-1and 15-2, the logical disk number 453, and the copy destination 454.

After the tables are updated, the updated tables are written in theconfiguration information storing area 152 of the storage system 15 in astep S7, thereby ending the processing.

The tables (configuration information) written in the configurationinformation storing area 152 of the storage system 15 are transferred,at given timing, to the storage system 25 of the secondary site 2 overthe inter-storage network 3 by the remote copy function of the storagesystem 15. A copy of configuration information of the primary site 1 isthus kept on the secondary site 2. The timing at which configurationinformation of the primary site 1 is copied to the secondary site 2 is,for example, each time a change is made to the configurationinformation.

The above processing by the configuration information fetching/storingfunction 111 is executed also on the secondary site 2, and theconfiguration information 40 of the secondary site 2 is updated in agiven configuration information storing area 252 of the storage system25.

FIG. 13 is a flow chart showing an example of processing performedthrough the re-creation function 112 in the configuration informationmanagement facility 210 of the secondary site 2. This processing isexecuted upon instruction from the administrator, upon notification of afailure from the primary site 1, or the like. This embodiment describesa case in which data in the configuration information storing area 152of the primary site 1 is backed up to the secondary site 2, and whensubsequently a failure occurs in the primary site 1, the secondary site2 takes over services of the primary site 1.

In a step S11, the management server 21 of the secondary site 2 readsthe copy of the configuration information 40 of the primary site 1 outof the configuration information storing area 252 (the logical disk LU12of FIG. 4) in the storage system 25.

In a step S12, the configuration information 40 of the secondary site 2is read out of the configuration information storing area 252 in thestorage system 25. In a step S13, the service management table 41 in theconfiguration information 40 of the primary site 1 and the servicemanagement table 41 in the configuration information 40 of the secondarysite 2 are compiled together. The resultant table, in which the servicesof the primary site 1 and the secondary site 2 shown in FIG. 6 arecombined, is denoted by 41′ and is shown in FIG. 14. According to theservice management table 41′, eight services have to be executed on twosites. The eight services are Service Eleven to Service Thirteen, whichhave been provided by the secondary site 2 in FIG. 6 before thesecondary site 2 takes over services of the primary site 1, plus threenew services added by taking over the primary site services.

In a step S14, the server management table 42 of the secondary site 2 isconsulted to judge whether or not there are as many servers whose status427 says “not in use” as the count of new services added (the servicesto be taken over). In other words, it is judged whether or not the countof the servers 23 that are on stand-by on the secondary site 2 is equalto or larger than the count of new services added. When there are enoughservers 23 available to take over all the primary site services, thesecondary site 2 is judged to have enough computer resources and theprocessing proceeds to a step S15. When the count of the servers 23 thatare on stand-by (not in use) is smaller than the count of new servicesadded, it is judged that there are not enough resources and theprocessing proceeds to a step S20.

In this embodiment, as shown in FIG. 6, the primary site 1 has fiveservers 13 providing Service One to Service Three whereas the secondarysite 2 has three servers 23 providing three services and two servers 23(23-2 and 23-4) on stand-by. While the secondary site 2 has to have atleast three servers 23 in order to take over the services of the primarysite 1, there are only two servers 23 that are on stand-by andaccordingly there are not enough resources available on the secondarysite 2.

In the step S20, which is the step subsequent to the step S14, when itis judged in the step S14 that there are not enough resources available,entries of the compiled service management table 41′ are sorted by theirpriority levels. In a step S21, services that have a higher prioritylevel than a preset priority level (e.g., 3) are chosen from the servicemanagement table 41′. The threshold priority level is set in advance bythe administrator of the secondary site 2 or the like.

Of the services that have been provided by the secondary site 2, thosethat are not chosen in the step S21 are halted, and the status 427 inthe server management table 42 is updated to “not in use” for theservers 23 that have been allocated to the services halted. Theallocation of the servers 23 to the services is thus canceled.

In the example of the service management table 41′ shown in FIG. 14,Service One and Service Two of the primary site 1 (site identifier: 1)and Service Eleven and Service Twelve of the secondary site 2 (siteidentifier: 2), four services in total, are chosen as services thatexceed the given priority level, 3, as a result of the steps S20 andS21. Service Thirteen which is not chosen is halted, and the allocationof Server Five (the server 23-5) to Service Thirteen is canceled byupdating the status 427 in the server management table 42 to “not inuse” for the server 23-5.

In a step S22, whether there are enough resources available or not ischecked by judging whether the count of unassigned servers 23 is equalto or larger than the count of the services chosen in the step S21 asones exceeding the given priority level. In the case where necessaryresources can be secured, the processing proceeds to the step S15. Inthe case where there are not enough resources available, the processingproceeds to a step S23.

In the step S23, since the secondary site 2 cannot handle services oftwo sites still after screening the services of the primary site 1 andthe secondary site 2 by their priority levels, services for which“recovery required” is entered as the recovery condition (re-creationcondition) 414 are chosen from the service management table 41′. Then,of the services that have been provided by the secondary site 2, thosefor which “recovery not required” is entered as the recovery condition414 are halted, and the status 427 in the server management table 42 isupdated to “not in use” for the servers 23 that have been allocated tothe services halted. The allocation of the servers 23 to the services isthus canceled. The steps S20 to S23 correspond to the service selectingfunction 113 of FIG. 5.

In the example of FIGS. 14 and 6, four services are chosen and it isjudged in the step S22 that the secondary site 2 equipped with fiveservers 23-1 to 23-5 has enough resources. The processing thereforeproceeds to the step S15.

In the step S15, the server selecting function 114 is executed to assignthe services chosen in the step S13 or S23 to the servers 23 of thesecondary site 2.

A description will be given with reference to a flow chart of FIG. 5 onan example of how the server selecting function 114 is executed in thestep S15. In a step S31, the site identifiers are read to designate, oneat a time, services of the primary site 1 out of the services selectedin the steps S13 to S23. In a step S32, performance information of aserver that has been allocated to the designated service is read. Serveridentifiers of the chosen servers are read out of the service managementtable 41′ of FIG. 14, and the server management table 42 of the primarysite 1 is read out of the configuration information storing area 252 toread the processor classification 422, the memory 423, and the device424 in entries of the read server identifiers.

In steps S33 to S35, the servers 23 for which “not in use” is entered asthe status 427 (free servers) are extracted from the server managementtable 42 of the secondary site 2, and then the processor classification422, the memory 423, and the device 424 are read.

In a step S36, whether or not there is a server that has been assignedto a chosen service and whose performance information (condition)matches that of a free server on the secondary site 2. When there arethe servers 23 that meet the condition, the processing proceeds to astep S38. When there are no servers 23 that meet the condition, theprocessing proceeds to a step S37.

In the step S37, a free server is chosen that has the same processorclassification 422 as and the closest performance information to theservers 13 that have been assigned to a chosen service on the primarysite 1. In this step, free servers may be chosen in a descending order.

In a step S38, the service of the primary site 1 that is designated inthe step S31 is added to the service management table 41 of thesecondary site 2. In a step S39, the status 427 is updated to “in use”for the free server chosen.

The server selecting function 114 of the management server 21 reads, outof the image storing area 253, a copy of software (boot images of OSs,applications and the like) used for the services of the primary site 1,and the servers 23 are allocated by performing the processing of thesteps S31 to S39 on every service of the primary site 1 that is chosenfrom the service management table 41′ of FIG. 14 one service at a time.Then the processing returns to a step S16 of FIG. 13.

The service-server allocation in the service management table 41′ ofFIG. 14 will be described with reference to FIG. 16.

In the case where Service One, Service Two, Service Eleven and ServiceTwelve, which exceed the given priority level, are chosen, the onlyservers that are in use (the status 427) in the server management table42 of the secondary site 2 are Server One (the server 23-1) and ServerThree (the server 23-3) whereas the rest of the servers, Server Two (theserver 23-2), Server Four (the server 23-4) and Server Five (the server23-5) are free servers.

Of the services of the primary site 1 that are decided to be taken overby the secondary site 2, Service One is associated with serveridentifiers 1 and 2. A secondary site server that is to take overService One is requested to meet such conditions that the processorclassification 422 is “CPU1”, which is associated with the serveridentifications 1 and 2 in the server management table 42 of FIG. 8, andthat the memory 423 is “2 GB”, which is associated with the serveridentifier 2 in FIG. 8. The server management table 42 of the secondarysite 2 is shown on the right hand side of FIG. 16, and the table issearched for the processor classification 422 starting from the top ofthe drawing toward the bottom of the drawing. The search reveals that aserver of the secondary site 2 whose processor classification 422 meetsthe condition is Server Three (the server 23-3, server identification:3). Accordingly, Server Three (the server 23-3) is assigned as a serverthat takes over Service One, the entry is added to the servicemanagement table 41 of the secondary site 2, and the status 427 forServer Three (the server 23-3) is updated to “in use” in the servermanagement table 42.

A secondary site server that is to take over Service Two is chosen asfollows:

Server Three (the server 13-3) that has been assigned to Service Two onthe primary site 1 has “CPU2” as the processor classification 422 and “4GB” as the memory 423. From the server management table 42 of thesecondary site 2, free servers whose processor classification 422 isCPU2 are extracted, and Server Five (the server 23-5) is chosen as onehaving a larger memory 423 than other extracted free servers. The thuschosen Server Five (the server 23-5) is assigned to Service Two, and themanagement tables are updated accordingly.

Through the above processing, despite the fact that the primary site 1and the secondary site 2 have different server configurations andprovide separate services independent of each other, formerly engagedservers are freed and assigned to services to be taken over by thesecondary site 2 so that as many high priority services as can behandled with resources of the secondary site 2 are executed.

After the server selecting function 114 finishes the step S15, theprocessing moves on to the step S16 of FIG. 13 to execute the networkswitch setting function 115. Details of the network switch settingfunction 115 will be described below with reference to FIG. 17.

In a step S41, a service of the primary site 1 is designated out of theservices selected in the steps S13 to S23.

In a step S42, one of the servers 23 of the secondary site 2 that isassigned to the designated service of the primary site 1 is chosen, andthe MAC address of the chosen one of the servers 23 is obtained from thedevice column 424 in the server management table 42 of FIG. 8.

In a step S43, the network switch management table 43 (FIG. 9) of thesecondary site 2 is searched for a network switch and a port that areassociated with the MAC address obtained in the step S42.

In a step S44, of VLAN numbers used for the services of the primary site1 that are taken over by the secondary site 2, a VLAN number that is notallocated to the secondary site 2 is obtained from the network switchmanagement table 43 of the secondary site 2.

In a step S45, the VLAN number obtained in the step S44 is allocated tothe port found as a result of the search of the step S43. In a step S46,the VLAN number allocated in the step S45 is set in the network switchmanagement table 43 of the secondary site 2.

In a step S47, it is judged whether or not the port found in the stepS43 is connected to plural different network switches 12. When the portis connected to plural different network switches 12, the VLAN numberset in the step S46 is allocated to a path of the found port, and arouting definition is set in a manner that allows the network switchesto communicate with each other. Then the network switch management table43 of the secondary site 2 is updated and the processing is ended.

The processing of the steps S41 to S48 is executed, one server at atime, for all of the servers 23 that are assigned to any one of servicesto be newly allocated on the secondary site 2.

Through the above processing, ports of the network switch 12 connectedto the servers 23 that execute services taken over by the secondary site2 are detected from the MAC addresses that the devices of these servers23 have. Then VLAN numbers (or VLAN-IDs) associated with the detectedports are obtained from the network switch management table 43, and theVLAN numbers are set such that VLAN numbers used on the primary site 1for the services taken over do not overlap with the VLAN settings of theIP network 26 on the secondary site 2.

In the case where VLAN number, or VLAN-ID, settings differ between theIP network 16 of the primary site 1 and the IP network 26 of thesecondary site 2, the secondary site 2 may use the exact VLAN numbersthat are used on the primary site 1.

The servers 23 are allocated by performing, one service at a time,processing of the steps S41 to S48 for every service of the primary site1 that is chosen from the service management table 41′ of FIG. 14. Thenthe processing returns to the step S16 of FIG. 13.

The processing of the steps S31 to S39 is performed as follows for theserver-service allocation in the service management table 41′ of FIG.14.

In the service management table 41′ of FIG. 14, when Service One andService Two of the primary site 1 are to be taken over by the secondarysite 2 and Service Eleven and Service Twelve of the secondary site 2 areto be continued, the server 23-4 assigned to Service One as shown inFIG. 16 has NIC5 and NIC6. From the MAC addresses of NIC5 and NIC6,numbers assigned to ports of the network switch 22 that are connected tothe server 23-4 are obtained to obtain an allocated VLAN number.

The VLAN number associated with NIC5 and NIC6 is compared against theVLAN number 10, which has been allocated on the primary site 1 toService One. When the former and the latter do not overlap, the VLANnumber 10, which has been allocated on the primary site 1 to ServiceOne, is set to the network switch 22 of the secondary site 2. On theother hand, when the VLAN number associated with NIC5 and NIC6 matchesthe VLAN number 10, which has been allocated on the primary site 1 toService One, a new VLAN number that is not the VLAN number 10 isobtained and set to the network switch 22.

In reproducing the configuration of the IP network 16 of the primarysite 1, the network switch setting function 115 sets the network switch22 as described above, so that VLAN numbers do not overlap and so thatthe environment of the IP network 26 for the server 23-4 that takes overService One of the primary site 1 is as close as possible to theenvironment on the primary site 1.

After the network switch setting function 115 finishes the step S16, theprocessing moves on to a step S17 of FIG. 13 to execute the storageswitch setting function 116. Details of the storage switch settingfunction 116 will be described below with reference to FIG. 18.

In a step S51, a service of the primary site 1 is designated out of theservices selected in the steps S13 to S23.

In a step S52, one of the servers 23 of the secondary site 2 that isassigned to the designated service of the primary site 1 is chosen, andthe WWN of the chosen one of the servers 23 is obtained from the devicecolumn 424 in the server management table 42 of FIG. 8.

In a step S53, the storage switch management table 44 (FIG. 10) of thesecondary site 2 is searched for the Fibre Channel switch 14 and a portthat are associated with the WWN obtained in the step S52.

In a step S54, of zone numbers used for the services of the primary site1 that are taken over by the secondary site 2, a zone number that is notallocated to the secondary site 2 is obtained from the storage switchmanagement table 44 of the secondary site 2.

In a step S55, the zone number obtained in the step S54 is allocated tothe port found as a result of the search of the step S53. In a step S56,the zone number allocated in the step S55 is set in the storage switchmanagement table 44 of the secondary site 2.

In a step S57, it is judged whether or not the port found in the stepS53 is connected to plural different Fibre Channel switches 14. When theport is connected to plural different Fibre Channel switches 14, thezone number set in the step S56 is allocated to a path of the foundport. Then the storage switch management table 44 of the secondary site2 is updated and the processing is ended.

The processing of the steps S51 to S58 is executed, one server at atime, for all of the servers 23 that are assigned to any one of servicesto be newly allocated on the secondary site 2.

Through the above processing, ports of the Fibre Channel switch 14connected to the servers 23 that execute services taken over by thesecondary site 2 are detected from the WWNs that the devices of theservers 23 have. Then zone numbers (or zone identifiers) associated withthe detected ports are obtained from the storage switch management table44, and the zone numbers are set such that zone numbers used on theprimary site 1 for the services taken over do not overlap with the zonenumbers of the SAN 17 on the secondary site 2.

In the case where zone number settings differ between the SAN 17 of theprimary site 1 and the SAN 27 of the secondary site 2, the secondarysite 2 may use the exact zone numbers that are used on the primary site1.

The processing of the steps S51 to S58 is performed as follows for theserver-service allocation in the service management table 41′ of FIG.14.

In the service management table 41′ of FIG. 14, when Service One andService Two of the primary site 1 are to be taken over by the secondarysite 2 and Service Eleven and Service Twelve of the secondary site 2 areto be continued, the server 23-4 assigned to Service One as shown inFIG. 16 has FCAs (not shown). From the WWNs of these FCAs, numbersassigned to ports of the SAN 27 that are connected to the server 23-4are obtained to obtain an allocated zone number.

The zone number associated with the FCAs of the server 23-4 is comparedagainst the zone number 10, which has been allocated on the primary site1 to Service One. When the former and the latter do not overlap, thezone number 10, which has been allocated on the primary site 1 toService One, is set to the Fibre Channel switch 24 of the secondary site2. On the other hand, when the zone number associated with the FCAs ofthe server 23-4 matches the zone number 10, which has been allocated onthe primary site 1 to Service One, a new zone number that is not thezone number 10 is obtained and set to the Fibre Channel switch 24.

In reproducing the configuration of the SAN 17 of the primary site 1,the storage switch setting function 116 sets the Fibre Channel switch 24as described above, so that zone numbers do not overlap and so that theenvironment of the SAN 27 for the server 23-4 that takes over ServiceOne of the primary site 1 is as close as possible to the environment onthe primary site 1.

After the storage switch setting function 116 finishes the step S17, theprocessing moves on to a step S18 of FIG. 13 to execute the storagesetting function 117. Details of the storage setting function 117 willbe described below with reference to FIG. 19.

In a step S61, a service of the primary site 1 is designated out of theservices selected in the steps S13 to S23.

In a step S62, one of the servers 23 of the secondary site 2 that isassigned to the designated service of the primary site 1 is chosen, anda WWN assigned to the FCA 133 of the chosen one of the servers 23 isobtained from the device column 424 in the server management table 42 ofFIG. 8.

In a step S63, the service management table 41 and storage managementtable 45 of the primary site 1 are read out of a copy of theconfiguration information 40 of the primary site 1 which has been backedup to the configuration information storing area 252 of the secondarysite 2. The read tables are consulted to obtain, from the column of thecopy destination 454, a site identifier and a system identifier that areassociated with a logical disk used on the primary site 1 for theservice designated in the step S61.

When the obtained site identifier indicates the secondary site 2 (siteidentifier: 2), the storage system 25 that is identified by the obtainedsystem identifier is chosen. The WWN obtained in the step S62 is set inthe column of the server identifier 452 of an entry for the chosenstorage system 25 in the storage management table 45 of the secondarysite 2. In the case where the storage management table 45 of thesecondary site 2 does not have an entry for the storage system 25 thatis chosen, a new entry is added to the table to set the systemidentifier and the server identifier.

In a step S64, a system identifier and a disk number that are associatedwith a logical disk used on the primary site 1 for the servicedesignated in the step S61 are obtained from the column of the copydestination 454 in (the copy of) the storage management table 45 of theprimary site 1 which is read in the step S63.

In a step S65, every disk number obtained in the step S64 is set as thedisk number 454 that is associated with the server identifier 452 set inthe step S63.

The processing of the steps S61 to S65 is executed, one server at atime, for all of the servers 23 that are assigned to any one of servicesto be newly allocated on the secondary site 2.

Through the above processing, logical disks of the storage system 25 towhich data of the primary site 1 has been backed up are allocated to theservers 23 that execute services taken over by the secondary site 2.

After the storage setting function 117 finishes the step S18, theprocessing moves on to a step S19 of FIG. 13. Now that thereconfiguration of the secondary site 2 is completed through theprocessing of the steps S20 to S23 and S15 to S18, the administrator ofthe secondary site 2 is notified in the step S19 of the information setin the tables (settings information). The notification is made bysending the settings information to, for example, a management terminalconnected to the IP network 26 of the secondary site 2.

The processing of the steps S61 to S65 is performed as follows for theserver-service allocation in the service management table 41′ of FIG.14.

In the service management table 41′ of FIG. 14, when Service One andService Two of the primary site 1 are to be taken over by the secondarysite 2 and Service Eleven and Service Twelve of the secondary site 2 areto be continued, the logical disks LU10, LU11 and LU13, to which data ofService One stored in a logical disk of the primary site 1 is copied,are allocated as shown in FIG. 11 to the server 23-4 assigned to ServiceOne as shown in FIG. 16.

As has been described, the configuration information management facility110 of the primary site 1 detects, in regular cycles, the configurationof the primary site 1 to update the configuration information 40 andstore the updated configuration information 40 in the configurationinformation storing area 152. Data of services performed by the servers13 of the primary site 1 is stored in the data storing area 151, andsoftware executed by the servers 13 is stored as a boot image in theimage storing area 153. The storage system 15 of the primary site 1 usesa remote copy function to copy data in the data storing area 151, theconfiguration information storing area 152 and the image storing area153 on the primary site 1 to the data storing area 251, theconfiguration information storing area 252, and the image storing area253 on the secondary site 2, respectively.

When a failure occurs in the primary site 1, the administrator or thelike activates the re-creation function 112 from the configurationinformation management facility 210 of the management server 21 on thesecondary site 2.

The re-creation function 112 allows the secondary site 2 to take overService One to Service Three of the primary site 1 all when thesecondary site 2 has enough resources available. In the case where thesecondary site 2 does not have enough resources available to take overall of the services of the primary site 1 while continuing providing itsown services, Service Eleven to Service Thirteen, the service managementtable 41 of the primary site 1 read out of the configuration informationstoring area 252 and the service management table 41 of the secondarysite 2 are compiled together. The compiled table, namely, the servicemanagement table 41′, is consulted to find services that exceed a givenpriority level, and only these services are taken over by the secondarysite 2.

In the case where the available resources are not enough still after thescreening of services by their priority levels, the service managementtable 41′ is searched for services for which “recovery required” isentered as the recovery condition 414, and these services are taken overfirst. The services thus chosen to be taken over by the secondary site 2are allocated to free resources of the secondary site 2 that are securedby halting some of the services of the secondary site 2. In this way,the optimum reconfiguration is achieved with the limited resources ofthe secondary site 2.

The data storing area 251, which keeps a copy of data in the datastoring area 151 of the primary site 1, is allocated to the servers 23that take over services of the primary site 1. Then the servers 23 arebooted with boot images in the image storing area 253, and services ofthe primary site 1 are thus resumed on the secondary site 2.

This embodiment employs remote copy in copying data and boot images, butit does not always have to be remote copy. Instead of remote copy, acopying server may be prepared to copy given data and images, forexample. Primary site configuration information, which in thisembodiment is stored in a storage system before being copied to thesecondary site 2 by remote copy, may instead be transferred directlyfrom the configuration information management facility 110 of theprimary site 1 to the configuration information management facility 210of the secondary site 2 over an inter-site network or the like.

Thus, in the first embodiment, the remote copy function of the storagesystem 15 on the primary site 1 is utilized to transfer primary site'sdata, configuration information 40, and boot images to the secondarysite 2 in advance, so that the primary site 1 can be quickly reproducedon the secondary site 2 from the transferred copy of the configurationinformation 40 in site recovery.

A change in configuration of the servers 13, the storage system 15, theIP network 16, and the SAN 17 on the primary site 1 does not cause thesecondary site 2 to fail to thereby always reproduce the latestconfiguration of the primary site 1 since the latest version of theconfiguration information 40 of the primary site 1 is kept transferredto the secondary site 2 through the remote copy function of the storagesystem 15. The primary site 1 can be reproduced automatically unlike theabove-described examples of prior art where human intervention isnecessary, and therefore the secondary site 2 can be reconfigured veryquickly. In application to recovery from disaster, in particular, thesecondary site 2 can take over the primary site 1 within a very shortperiod of time, which shortens the service interruption periodsignificantly and minimizes the damage to the company or organization.

Second Embodiment

FIG. 20 is a system configuration diagram according to a secondembodiment of this invention as applied to server consolidation (serverintegration).

Shown in FIG. 20 is an example of integrating old computer systems onSite One (denoted by 5 in the drawing) and Site Two (denoted by 6 in thedrawing) into a new computer system on Site Three.

Site One provides Service One to Service Three whereas Site Two providesService Ten and Service Eleven. On Site One and Site Two each, theconfiguration information fetching/storing function 111 updates theconfiguration information 40 of the site in the storage system 15. As inthe first embodiment, the storage system 15 of Site One and the storagesystem 15 of Site Two respectively use remote copy to store and updatecopies of their sites' data, configuration information 40, and bootimages in the storage system 25 of Site Three.

At the start of the server integration, the re-creation function 112 ofthe configuration information management facility 210 is activated inthe management server 21 of Site Three to reproduce Site One and SiteTwo on Site Three from the copied configuration information 40 of SiteOne and the copied configuration information 40 of Site Two.

The re-creation function 112 compiles together the service managementtable 41 of Site One and the service management table 41 of Site Two toobtain the service management table 41′ as in the first embodiment. Inthe manner described in the first embodiment, resources of Site Threeare assigned to Service One to Service Three and Service Ten and ServiceEleven in accordance with how many resources are available on SiteThree.

Since the services are allocated to the resources in the same manner asdescribed in the first embodiment, redundant descriptions are omitted.The difference between the first embodiment and the second embodiment isthat Site Three into which other sites are integrated does not have itsown service to provide and to be halted before the allocation.

In the case where new Site Three has enough resources available, allservices of Site One and Site Two are taken over by Site Three. In thecase where Site Three does not have enough resources available, servicesare allocated to resources in the order of priority written in theservice management table 41′. If there are still not enough resourcesavailable, services for which “recovery required” is entered as therecovery condition 414 are extracted from the service management table41′ to be taken over by Site Three first.

The above processing enables Site Three to reproduce and integrate SiteOne and Site Two as soon as data, the configuration information 40, andboot images of Site One and Site Two, which hold old computer systems,finish being transferred to the storage system 25 of Site Three throughremote copy by the storage system 15 of each of the old sites.

This embodiment employs remote copy in copying data and boot images, butit does not always have to be remote copy. Instead of remote copy, acopying server may be prepared to copy given data and images, forexample.

As in the first embodiment, servers can automatically be integrated bythe re-creation function 112 of Site Three without needing theadministrator to have detailed knowledge about the configuration of SiteOne and Site Two. Thus, the enormous amount of labor and time requiredin conventional server integration is cut down greatly and a newcomputer system can start operating in significantly less time afterintroduction.

Third Embodiment

FIGS. 21 to 25 show a third embodiment of this invention in which aserver partitioning function is added to the service selecting function113 of the first embodiment. The rest of the third embodiment isconfigured the same way as the first embodiment.

In the third embodiment, when the secondary site 2 does not have enoughresources to assign to services for which “recovery required” is enteredas the recovery condition 414, the service selecting function 113 of there-creation function 112 creates plural virtual servers by logicalpartitioning of a server, or creates plural virtual computers in aserver, so that services for which “recovery required” is entered as therecovery condition 414 are allocated to resources of the secondary site2 and essential services are resumed.

In FIG. 21, the service selecting function 113 described in the firstembodiment with reference to the steps S20 to S23 of the flow chart ofFIG. 13 is a sub-routine, and a server partitioning function is newlyadded.

Steps S20 to S23 of FIG. 21 are the same as those of FIG. 13 describedin the first embodiment, and the management server 21 of the secondarysite 2 reads the service management table 41 of the primary site 1 outof the storage system 25 to combine the read table with the servicemanagement table 41 of the secondary site 2 and obtain the servicemanagement table 41′ shown in FIG. 14.

Since it is judged in the step S14 of FIG. 13 that the secondary site 2does not have enough resources available, services in the compiledservice management table 41′ are sorted by their priority to choose, inthe step S21, services that exceed a preset priority level (3, forexample).

In the step S22, it is judged whether or not there are enough resourcesto execute services chosen according to their priority levels. When thesecondary site 2 does not have enough resources available, theprocessing proceeds to the step S23, where services for which “recoveryrequired” is entered as the recovery condition 414 are chosen first.

On the other hand, when it is judged in the step S22 that there areenough resources available, services that are not chosen in the step S21are halted and the status 427 in the server management table 42 isupdated to “not in use” for the servers 23 that have been assigned tothe services halted. The allocation of the servers 23 to the services isthus canceled. Thereafter, the sub-routine is ended and the processingmoves on to the step S15 (the server selecting function) of FIG. 13.

In a step S24, it is judged whether or not the secondary site 2 hasenough resources to execute services for which “recovery required” isentered as the recovery condition 414. When there are enough resourcesavailable, services for which “recovery not required” is entered as therecovery condition 414 are halted and the status 427 in the servermanagement table 42 is updated to “not in use” for the servers 23 thathave been assigned to the services halted. The allocation of the servers23 to the services is thus canceled. Thereafter, the sub-routine isended.

On the other hand, when the secondary site 2 does not have enoughresources to assign to services for which “recovery required” is enteredas the recovery condition 414, the processing proceeds to a step S25,where a server is partitioned. After necessary resources are secured bythe server partitioning in the step S25, the sub-routine is ended.

FIG. 22 is a flow chart of the server partitioning function executed inthe step S25 of FIG. 21.

Prior to the server partitioning, services for which “recovery notrequired” is entered as the recovery condition 414 are halted, and thestatus 427 in the server management table 42 is updated to “not in use”for the servers 23 that have been assigned to the services halted, tothereby cancel the allocation of the servers 23 to the services.

In a step S251, the server management table 42 is searched for freeservers whose status 427 is “not in use” to choose the servers 23 whoseprocessors can be divided for logical partitioning (LPAR). In otherwords, a free server is checked for whether it has plural processors,and the servers 23 that have plural processors (or processor cores) eachare chosen to be logically partitioned.

In a step S252, logical sections are set in a chosen server inaccordance with how many processors the server has, and the processorsare divided (logical partitioning). The count of logical sections is setin advance in accordance with the count of processors. For example, whena server has four processors or less, two logical sections are set inthe server and, when there are eight processors, four logical sectionsare set.

In a step S253, the NIC 136, the FCA 133 and other devices of a chosenserver (physical computer) 23-x are allocated as shown in FIG. 23 to thelogical sections created in the step S252, to thereby create LogicalServer One and Logical Server Two. Shown in FIG. 23 is a case in which apartitioning function 233 (middleware of the like) divides fourprocessors 231 into two logical sections, and a half of the memory 232as well as a half of the devices including the NIC 136 and the FCA 133are given to each of the two logical sections to create Logical ServerOne (2301) and Logical Server Two (2302).

In a step S254, Logical Server One and Logical Server Two created in thestep S253 are added to the server management table 42, and then servicesfor which “recovery required” is entered as the recovery condition 414are allocated to the chosen server 23-x and to the logical servers 2301and 2302.

FIG. 25 shows a part of the server management table 42 of when thelogical servers 2301 and 2302 are created in one of the physicalcomputers 23.

In FIG. 25, the physical computer 23-x of FIG. 23 has a serveridentifier 1 whereas the logical servers (logical computers in FIG. 25)2301 and 2302 have server identifiers 2 and 3, respectively. After thelogical servers are created, the status of the physical computer, whichhas the server identifier 1, is changed to “in use” in the servermanagement table 42. Then entries for the server identifiers 2 and 3 areadded to the table. A half of the processors, memory, devices, andstorage of the physical computer are allocated to each of the twological servers. After services are assigned to the logical servers, thestatus 427 is changed to “in use” in the entries for the serveridentifiers 2 and 3.

After the logical partitioning is finished, whether there are enoughresources available or not is judged again in a step S255. This judgingstep is taken when, for example, no servers 23 are found in the stepS251 that can be logically partitioned. When it is judged in the stepS255 that the secondary site 2 does not have enough resources available,the processing proceeds to a step S256 to create virtual computers(virtual machines).

In the step S256, the server management table 42 is searched for freeservers whose status 427 is “not in use” to choose the servers 23 thatcan produce virtual computers. In other words, a free server is checkedfor whether it has a processor capable of running plural OSs, and theservers 23 that are judged from the processor classification 422 to havea preset level of performance are chosen. The choice may be made suchthat the servers 23 that have processors whose drive frequency andmemory capacity exceed a preset threshold are chosen.

In a step S257, a host OS is activated on a chosen server 23-x and asmany guest OSs as determined by the performance of the processor (twoguest OSs, for example) are activated to create virtual computers.

In a step S258, the NIC 136, the FCA 133 and other devices of a chosenserver (physical computer) 23-x are allocated as shown in FIG. 24 to thevirtual computers (logical servers in FIG. 24), 2301 and 2302, createdin the step S257, to thereby create Logical Server One and LogicalServer Two. Shown in FIG. 24 is an example in which two virtualcomputers (logical servers) are run on a virtual computer facility 234.The virtual computer facility 234 allocates the memory 232 as well asthe devices including the NIC 136 and the FCA 133 to Logical Server One(2301) and Logical Server Two (2302).

In a step S259, Logical Server One and Logical Server Two created in thestep S258 are added to the server management table 42 as in the logicalpartitioning described above, and then services for which “recoveryrequired” is entered as the recovery condition 414 are assigned to thechosen server 23-x and to the logical servers 2301 and 2302.

As has been described, essential services can be taken over by thesecondary site 2 despite shortage of available resources by applyinglogical partitioning or virtual computers to the servers 23 of thesecondary site 2.

Fourth Embodiment

FIGS. 26 to 28 show a fourth embodiment of this invention in which thestorage setting function 117 of the first embodiment utilizes are-mapping function of the storage system 25 to replace logical disknumbers allocated to the servers 23 of the secondary site 2 with virtualdisk numbers, so that the same logical disk numbers as on the primarysite 1 are allocated. The rest of the fourth embodiment is configuredthe same way as the first embodiment.

To some of applications run on the servers 13 of the primary site 1,fixed logical disks are applied. When such applications are included inboot images copied to the secondary site 2, the applications may notfunction upon site recovery unless the secondary site 2 has the samelogical disk numbers as the primary site 1.

The storage systems 15 and 25 have, as one of security functions, are-mapping function with which arbitrary virtual disk numbers areassigned to allocated logical disk numbers (hereinafter referred to asphysical disk numbers), so that the servers 13 and 23 identify logicaldisks by virtual disk numbers.

FIG. 26 shows an example of the storage management table 45 of thesecondary site 2. In this example, the primary site 1 has two storagesystems (storage identifier: 1 and 2) in which logical disks are givenphysical disk numbers (4532) LU5 to LU7, LU10, LU11, LU17, LU21 andLU22.

Logical disks having virtual disk numbers (4531) 0, 1, and 3 areallocated to one of the servers 13 that executes Service One and thathas WWN1 as its server identifier.

The storage system 25 of the secondary site 2 has a similarconfiguration, and arbitrary virtual disk numbers 4531 can be assignedto physical disk numbers 4532 in the storage system 25 by the re-mappingfunction.

The re-mapping function is, as shown in FIG. 28, executed by a diskmapping facility 1502 of the security function 1501 in each of thestorage systems 15 and 25. The disk mapping facility 1502 has a diskmapping table 1503 composed of a physical disk number 1506, whichindicates a number assigned to a physical disk in the storage system, avirtual disk number 1505, which indicates a virtual disk number assignedto the physical disk number 1506, and a server identifier 1505, whichindicates the identifier of a server to which logical disks identifiedby the virtual disk number 1505 are allocated. The disk mapping facility1502 manages the virtual disk number 1505 and the physical disk number1506 within the storage system, and manages server identifiers as well.

FIG. 27 shows an example of how the storage setting function 117 usingthe re-mapping function is executed on the secondary site 2. The stepsS61 to S64 of FIG. 27 are the same as those in FIG. 19, whichillustrates the storage setting function of the first embodiment.

In the step S61, a service of the primary site 1 is designated out ofthe services selected in the steps S13 to S23 of FIG. 13 in the firstembodiment.

In the step S62, one of the servers 23 of the secondary site 2 that isassigned to the designated service of the primary site 1 is chosen, anda WWN assigned to the FCA 133 of the chosen one of the servers 23 isobtained from the device column 424 in the server management table 42 ofthe secondary site 2.

In the step S63, the service management table 41 and storage managementtable 45 of the primary site 1 are read out of a copy of theconfiguration information 40 of the primary site 1 which has been backedup to the configuration information storing area 252 of the secondarysite 2. The read tables are consulted to obtain, from the column of thecopy destination 454, a site identifier and a system identifier that areassociated with a logical disk used on the primary site 1 for theservice designated in the step S61.

When the obtained site identifier indicates the secondary site 2 (siteidentifier: 2), the storage system 25 that is identified by the obtainedsystem identifier is chosen. The WWN obtained in the step S62 is set inthe column of the server identifier 452 of an entry for the chosenstorage system 25 in the storage management table 45 of the secondarysite 2. In the case where the storage management table 45 of thesecondary site 2 does not have an entry for the storage system 25 thatis chosen, a new entry is added to the table to set the systemidentifier and the server identifier.

In the step S64, a system identifier and a disk number that areassociated with a logical disk used on the primary site 1 for theservice designated in the step S61 are obtained from the column of thecopy destination 454 in (the copy of) the storage management table 45 ofthe primary site 1 which is read in the step S63.

In a step S65A, every disk number obtained in the step S64 is expressedas the virtual disk numbers 4531 and assigned to the physical disknumbers 4532 that are associated with the server identifier 452 set inthe step S63. Then the management server 21 instructs the storage system25 to reflect the association relation set between the virtual disknumbers 4531, the physical disk numbers 4532, and the server identifiersin the storage management table 45.

The processing of the steps S61 to S65A is executed, one server at atime, for all of the servers 23 that are assigned to any one of servicesto be newly allocated on the secondary site 2.

Accordingly, when the secondary site 2 is to recover the primary site 1where applications of the servers 13 that execute Service One accesslogical disks having logical disk numbers 0, 1, and 3, the virtual disknumbers 4531 of the disks that are accessed by the server 13-1 on theprimary site 1 are assigned to the physical disk numbers 4532 that arethe copy destinations of the virtual disk numbers (logical disk numbers)0, 1, and 3. The assigned virtual disk numbers 4531 are associated withthe identifiers of the servers 23 that take over Service One of theprimary site 1.

The processing of the steps S61 to S65A makes it possible to assign thevirtual disk number 1505 in a manner that gives the storage system 25 ofthe secondary site 2 the same logical disk numbers as on the primarysite 1 when logical disk numbers of disks accessed by applications arefixed. Therefore, an application run on the servers 23 can access thestorage system 25 in seemingly the same environment as the primary site1, and the primary site 1 is recovered easily and quickly irrespectiveof the type of the application.

The first, second and fourth embodiments show an example in which theservice management table 41 of the primary site 1 and the servicemanagement table of the secondary site 2 are compiled together toexecute services of the two sites in accordance with the priority andrecovery condition 414 of the compiled table. Alternatively, services ofthe primary site 1 may be put above services of the secondary site 2.

In FIG. 1, an IP network of the like may connect the management server11 of the primary site 1 with the management server 21 of the secondarysite 2, thereby enabling the management server 21 to detect a failure inthe management server 11 and subsequently activate the re-creationfunction 112.

In the embodiments described above, the configuration informationmanagement facilities 110 and 210 are run on the management servers 11and 21 installed on the primary site 1 and the secondary site 2,respectively. Alternatively, the configuration information managementfacility 110 may be run on one of the servers 13 arbitrarily selectedwhereas the configuration information management facility 210 is run onone of the servers 23 arbitrarily chosen.

As has been described, this invention makes it possible to quicklyreproduce one computer system with another computer system bytransferring, in advance, configuration information as well as data ofthe former computer system to the latter computer system. The inventionis therefore applicable to disaster recovery and server integration.

While the present invention has been described in detail and pictoriallyin the accompanying drawings, the present invention is not limited tosuch detail but covers various obvious modifications and equivalentarrangements, which fall within the purview of the appended claims.

1. A method of reproducing a configuration of a computer systemcomprising: a first computer system, which comprises server devices anda storage system, and executes at least one service; and a secondcomputer system, which comprises server devices and a storage system,and executes the at least one service that has been executed by thefirst computer system, the method comprising the followingcomputer-implemented steps: collecting an association relation betweenthe at least one service and each of the server devices that are run inthe first computer system, and collecting, from among information pieceson components of the each of the server devices of the first computersystem, at least one of a processor classification, memory information,and device information, to thereby obtain the collected associationrelation and the information pieces on the components of the each of theserver devices as configuration information of the first computersystem; copying data of the at least one service of the first computersystem and the configuration information to the second computer system;and assigning, in the second computer system, the at least one serviceof the first computer system to each of the server devices of the secondcomputer system based on the copied configuration information of thefirst computer system, wherein the assigning the at least one service ofthe first computer system to the each of the server devices of thesecond computer system comprises: searching, based on the copiedconfiguration information of the first computer system, the secondcomputer system for one of the server devices of the second computersystem having at least one of a processor classification, memoryinformation, and device information, which coincides with at least onecondition of the processor classification, the memory information, andthe device information of the first computer system, and obtaining,based on the device information, a device identifier of a device of theone of the server devices of the second computer system, which iscoupled to the storage system of the second computer system; and settingthe device identifier to the storage system of the second computersystem to associate the one of the server devices of the second computersystem, which has been searched for, with the storage system of thesecond computer system.
 2. The method of reproducing a computer systemconfiguration according to claim 1, wherein the assigning of services ofthe first computer system to server devices of the second computersystem is performed when a failure occurs in the first computer system.3. The method of reproducing a computer system configuration accordingto claim 1, wherein the first computer system includes plural computersystems, and wherein the assigning of services of the first computersystem to server devices of the second computer system includesallocating services of the first computer system to server devices ofthe second computer system in a manner that integrates the pluralcomputer systems constituting the first computer system into the secondcomputer system.
 4. The method of reproducing a computer systemconfiguration according to claim 1, wherein the copying of data of theservices of the first computer system and the configuration informationto the second computer system includes copying also images of softwareexecuted by the server devices of the first computer system.
 5. Themethod of reproducing a computer system configuration according to claim1, wherein the assigning of services of the first computer system toserver devices of the second computer system includes: assigning virtualdisk numbers of the storage system of the first computer system toserver devices of the second computer system based on the serverdevice-storage system association relations in the first computersystem.
 6. A computer system, comprising: a first computer system, whichcomprises server devices and a storage system, and executes at least oneservice; and a second computer system, which comprises server devicesand a storage system, and executes the at least one service that hasbeen executed by the first computer system, wherein the first computersystem further comprises a first management unit which is configured to:collect an association relation between the at least one service andeach of the server devices that are run in the first computer system,and collect, from among information pieces on components of the each ofthe server devices of the first computer system, at least one of aprocessor classification, memory information, and device information, tothereby obtain the collected association relation and the informationpieces on the components of the each of the server devices asconfiguration information of the first computer system; and copy data ofthe at least one service of the first computer system and theconfiguration information to the second computer system, wherein thesecond computer system further comprises a second management unit forassigning the at least one service of the first computer system to eachof the server devices of the second computer system based on the copiedconfiguration information of the first computer system, and wherein thesecond management unit is configured to: search, based on the copiedconfiguration information of the first computer system, the secondcomputer system for one of the server devices of the second computersystem having at least one of a processor classification, memoryinformation, and device information, which coincides with at least onecondition of the processor classification, the memory information, andthe device information of the first computer system, and obtain, basedon the device information, a device identifier of a device of the one ofthe server devices of the second computer system, which is coupled tothe storage system of the second computer system; and set the deviceidentifier to the storage system of the second computer system toassociate the one of the server devices of the second computer system,which has been searched for, with the storage system of the secondcomputer system.
 7. The computer system according to claim 6, whereinthe second management unit assigns the at least one service of the firstcomputer system to the each of the server devices of the second computersystem when a failure occurs in the first computer system.
 8. Thecomputer system according to claim 6, wherein the first computer systemcomprises a plurality of computer systems, and wherein the secondmanagement unit assigns the at least one service of the first computersystem to the each of the server devices of the second computer systemso as to integrate the plurality of computer systems constituting thefirst computer system into the second computer system.
 9. The computersystem according to claim 6, wherein the first management unit furthercopies images of software executed by the server devices of the firstcomputer system.
 10. The computer system according to claim 6, whereinthe second management unit assigns virtual disk numbers of the storagesystem of the first computer system to the server devices of the secondcomputer system based on an association relation between the each of theserver devices and the storage system of the first computer system. 11.A method of reproducing a computer system configuration to cause asecond computer system to execute one or more services that have beenexecuted by a first computer system, the first computer including serverdevices and a storage system, the second computer including serverdevices and a storage system, the method comprising the followingcomputer-implemented steps: using a first configuration informationmanager of the first computer system to collect a set of firstassociation relations between the one or more services that are executedby the first computer system and the server devices of the firstcomputer system; using the first configuration information manager ofthe first computer system to collect a set of second associationrelations among the server devices of the first computer system, thestorage system of the first computer system, and a set of firstprocessor classifications of the server devices of the first computersystem; using the first configuration information manager of the firstcomputer system to collect a third association relation between thestorage system of the first computer system and the storage system ofthe second computer system; using the first configuration informationmanager of the first computer system to store the set of firstassociation relations, the set of second association relations, and thethird association relation in the storage system of the first computersystem as configuration information of the first computer system;copying data of the one or more services that are executed by the firstcomputer system and the configuration information of the first computersystem from the storage system of the first computer system to thestorage system of the second computer system; using a secondconfiguration information manager of the second computer system tocollect a set of fourth association relations between one or moreservices that are executed by the second computer system and the serverdevices of the second computer system; using the second configurationinformation manager of the second computer system to collect a set offifth association relations among the server devices of the secondcomputer system, the storage system of the second computer system, and aset of second processor classifications of the server devices of thesecond computer system; using the second configuration informationmanager of the second computer system to store the set of fourthassociation relations and the set of fifth association relations in thestorage system of the second computer system as configurationinformation of the second computer system; using the secondconfiguration information manager of the second computer system toselect, based on the configuration information of the first computersystem copied to the storage system of the second computer system, a setof server devices from the server devices of the second computer systemfor executing the one or more services that have been executed by thefirst computer system; using the second configuration informationmanager of the second computer system to assign the one or more servicesexecuted by the first computer system to the selected set of serverdevices of the second computer system; and using the secondconfiguration information manager of the second computer system toassociate the selected set of server devices of the second computersystem to which the one or more services executed by the first computersystem are assigned with the storage system of the second computersystem, and wherein the second configuration information manager of thesecond computer system selects the selected set of server devices of thesecond computer system by: referring to the second set of associationrelations of the configuration information of the first computer systemcopied to the storage system of the second computer system to obtain theset of first processor classifications of the server devices of thefirst computer system used by the first computer system for the one ormore services executed by the first computer system as performanceinformation on the server devices; comparing the obtained set of firstprocessor classifications with the set of second processorclassifications to select the server devices of the second computersystem having a second processor classification that matches with afirst processor classification of the obtained set of first processorclassifications as the selected set of server devices of the secondcomputer system; and assigning the one or more services of the firstcomputer system to the server devices of the selected set of serverdevices of the second computer system according to the matching betweenthe set of second processor classifications and the obtained set offirst processor classifications.
 12. The method of reproducing acomputer system configuration according to claim 11, wherein the firstcomputer system and the second computer system each have a networkdevice, wherein the first configuration information manager of the firstcomputer system stores the configuration information of the firstcomputer system in the storage system of the first computer system by:collecting a set of service-virtual network identifier associationrelations between services executed by the first computer system andidentifiers of virtual networks to which the services belong; andstoring the set of service-virtual network identifier associationrelations as a part of the configuration information in the storagesystem of the first computer system, and wherein the secondconfiguration information manager of the second computer system assignsthe one or more services executed by the first computer system to theselected set of server devices of the second computer system by setting,based on the configuration information copied to the second computersystem, the network device of the second computer system such that theserver devices of the second computer system that are assigned to theservices belong to the virtual networks to which the services belong.13. The method of reproducing a computer system configuration accordingto claim 12, wherein the second configuration information manager of thesecond computer system sets the network device of the second computersystem by obtaining, when a virtual network identifier of the networkdevice of the first computer system and a virtual network identifier ofthe network device of the second computer system overlap, a new virtualnetwork identifier that is different from the virtual network identifierof the network device of the first computer system.
 14. The method ofreproducing a computer system configuration according to claim 11,wherein the first configuration information manager of the firstcomputer system stores the configuration information of the firstcomputer system in the storage system of the first computer system bycollecting information indicating a type of the server devices of thefirst computer system, and storing the information as a part of theconfiguration information in the storage system of the first computersystem, and wherein the second configuration information manager of thesecond computer system assigns the one or more services executed by thefirst computer system to the selected set of server devices of thesecond computer system by assigning, based on the information indicatinga type of the server devices that is contained in the configurationinformation copied to the second computer system, server devices of thesecond computer system that are of the same type as the server devicesof the first computer system.
 15. The method of reproducing a computersystem configuration according to claim 11, wherein copying data of theone or more services that are executed by the first computer system andthe configuration information of the first computer system from thestorage system of the first computer system to the storage system of thesecond computer system includes copying the configuration information tothe second computer system when there is a change in configuration ofthe first computer system.
 16. The method of reproducing a computersystem configuration according to claim 11, wherein the first computersystem and the second computer system each have a storage switch, whichconnects the server devices with the storage system, wherein the firstconfiguration information manager of the first computer system storesthe configuration information of the first computer system in thestorage system of the first computer system by: collecting service-zoneidentifier association relations between services executed by the firstcomputer system and identifiers of storage switch zones to which theservices belong; and storing the service-zone identifier associationrelations as a part of the configuration information in the storagesystem of the first computer system, and wherein the secondconfiguration information manager of the second computer system assignsthe one or more services executed by the first computer system to theselected set of server devices of the second computer system by setting,based on the configuration information copied to the second computersystem, the storage switch of the second computer system such that theserver devices of the second computer system that are assigned to theservices belong to the zones.
 17. The method of reproducing a computersystem configuration according to claim 16, wherein setting of thestorage switch of the second computer system includes setting thestorage switch of the second computer system by obtaining, when a zoneidentifier of the storage switch of the first computer system and a zoneidentifier of the storage switch of the second computer system overlap,a new zone identifier that is different from the zone identifier of thestorage switch of the first computer system.
 18. The method ofreproducing a computer system configuration according to claim 11,wherein the set of first association relations includes priority levelsset for each service in advance, and wherein the second configurationinformation manager of the second computer system assigns the one ormore services executed by the first computer system to the selected setof server devices of the second computer system by assigning services inthe order of the set priority in a case where not all of the services ofthe first computer system can be assigned to the server devices of thesecond computer system.
 19. The method of reproducing a computer systemconfiguration according to claim 11, wherein the set of firstassociation relations includes a reproduction condition, which is setfor each service in advance to indicate whether or not the service isrequired to be executed in the reproduced computer system, and whereinthe second configuration information manager of the second computersystem assigns the one or more services executed by the first computersystem to the selected set of server devices of the second computersystem by assigning services whose execution is required according tothe reproduction condition first in a case where not all of the servicesof the first computer system can be assigned to the server devices ofthe second computer system.
 20. The method of reproducing a computersystem configuration according to claim 19, wherein the secondconfiguration information manager of the second computer system assignsthe one or more services executed by the first computer system to theselected set of server devices of the second computer system further by,when not all of the services whose execution is required according tothe reproduction condition can be assigned to the server devices of thesecond computer system, partitioning the server devices of the secondcomputer system to create logical servers, and assigning the services tothe created logical servers as well as to physical servers.
 21. Themethod of reproducing a computer system configuration according to claim11, wherein the second configuration information manager of the secondcomputer system assigns the one or more services executed by the firstcomputer system to the selected set of server devices of the secondcomputer system upon a failure occurring in the first computer system.22. The method of reproducing a computer system configuration accordingto claim 11, wherein the first computer system includes a plurality ofcomputer systems, and wherein the second configuration informationmanager of the second computer system assigns the one or more servicesexecuted by the first computer system to the selected set of serverdevices of the second computer system by allocating services of thefirst computer system to server devices of the second computer system ina manner that integrates the plurality of computer systems constitutingthe first computer system into the second computer system.
 23. Themethod of reproducing a computer system configuration according to claim11, wherein copying data of the one or more services that are executedby the first computer system and the configuration information of thefirst computer system from the storage system of the first computersystem to the storage system of the second computer system includescopying images of software executed by the server devices of the firstcomputer system.
 24. The method of reproducing a computer systemconfiguration according to claim 11, wherein the first computer systemincludes a plurality of computer systems, and wherein the secondconfiguration information manager of the second computer system assignsthe one or more services executed by the first computer system to theselected set of server devices of the second computer system byassigning virtual disk numbers of the storage system of the firstcomputer system to server devices of the second computer system based onthe second association relations.
 25. The method of reproducing acomputer system configuration according to claim 11, the firstconfiguration information manager of the first computer system collectsthe set of second association relations by collecting first processorperformance information on the server devices of the first computersystem, first memory information on the server devices of the firstcomputer system, and first device information on the server devices ofthe first computer system in addition to the set of second associationrelations; and the second configuration information manager of thesecond computer system collects the set of fifth association relationsby collecting second processor performance information on the serverdevices of the second computer system, second memory information on theserver devices of the second computer system, and second deviceinformation on the server devices of the second computer system inaddition to the fifth association relations.
 26. The method ofreproducing a computer system configuration according to claim 25,wherein the second configuration information manager of the secondcomputer system selects the selected set of server devices of the secondcomputer system further by: referring to the second associationrelations of the configuration information of the first computer systemcopied to the storage system of the second computer system to obtain thefirst processor performance information, the first memory information,and the first device information; comparing first performanceinformation including the second processor performance information, thesecond memory information, and the second device information with secondperformance information including the first processor performanceinformation, the first memory information, and the first deviceinformation; and assigning the one or more services of the firstcomputer system to server devices in the second computer system havingperformance information close to the performance information of theserver devices of the first computer system.